[frontend] Disable cache when interpreter is enabled #8499
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When TRITON_INTERPRET=1, the cache should always be disabled in both cases, cache_results=true and TRITON_CACHE_AUTOTUNING=1. Otherwise, there is an error in `check_disk_cache` since it is searching for a JITFunction which is not available. Signed-off-by: Rebecca Pelke <[email protected]>
peterbell10
approved these changes
Oct 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
TRITON_INTERPRET=1, the cache should always be disabled (in both cases,cache_results=trueandTRITON_CACHE_AUTOTUNING=1). Otherwise, there is an error incheck_disk_cachesince it is searching for aJITFunctionwhich is not available.This has been discussed in #6678 already but the introduced changes still enable caching results when
cache_results=true.New contributor declaration
I am not making a trivial change, such as fixing a typo in a comment.
I have written a PR description following these
rules.
I have run
pre-commit run --from-ref origin/main --to-ref HEAD.Select one of the following.
/testforlittests/unittestfor C++ tests/python/testfor end-to-end testsSelect one of the following.
littests.littests I have added follow these best practices,including the "tests should be minimal" section. (Usually running Python code
and using the instructions it generates is not minimal.)